Problem moving objects within a formal module.

I have several objects with children in a formal module that I am trying to move from level 4 to level 1. I am able to move the objects and their children to level 1 and save the module, but when the module is closed and re-opened, the objects have moved back to level 4.

I archived this module from our production environment and restored the module in a test environment. When the module was opened, all objects that were moved from the level 4 to level 1 were displayed at level 1. The archived module was then restored to our production environment as a different name. Once again, when the restored module was opened, all objects that were moved from the level 4 to level 1 were displayed at level 1.

Currently have over 500+ modules and I have not had this issue within any of the other modules. Using Version 8.3 with Patch 1 and have scheduled to install Patch 2 to the server and clients next week.

Have any of you come across this issue. Any suggestions would be appreciated before I submit this as a defect.

Thanks in advance.

Todd
Todd_Griffin - Wed Dec 03 17:57:00 EST 2008

Re: Problem moving objects within a formal module.
kbmurphy - Thu Dec 04 11:56:42 EST 2008

Todd,

Deja vu.

move object via DXL not sticking

Log the bug.

Re: Problem moving objects within a formal module.
Todd_Griffin - Thu Dec 04 14:06:03 EST 2008

Kevin,

Thanks for the response, I will log the bug.

I discovered another twist this morning within the same module. I opened the module in Exclusive edit, display the module explorer and the Object Level attribute. These objects are displayed at Level 4. Switch the edit mode to Read only and the objects are still displayed at Level 4, but when I switch back to Exclusive edit, these Level 4 object are then displayed at Level 1. I save and close the module. When I re-open the module, these objects are at Level 4 again.

Todd

Re: Problem moving objects within a formal module.
Todd_Griffin - Mon Dec 15 12:28:45 EST 2008

Want to share the response from DOORS support on the case submitted (KM2091785). Their product development though this was a similar issue that has been fixed in DOORS 9, but they have a workaround for 8.x. Here is an excerpt from the defect report that was initially raised:

"The problem only shows up when an object follows another deleted object, and is also the first object to reference a link module (in this case DOORS Links) whose last linkset is invalid (e.g. references purged modules). In such cases, the formal module object is attached to the last loaded object before it instead of its proper place. (This is happening when the link module is loaded on the fly as a result of links in the formal module object.)

With the 8.3 client, if you open the DOORS Links module explicitly, before opening the formal module, then the formal module loads OK. If you re-save the DOORS Links module, that should fix the problem with this object"

So what you will need to do is open and save the link modules which are related to this formal module. When you then reopen the formal module and then start moving objects, you should now survive a reopening of the module.

Performing this workaround for DOORS 8.3 fixed this issue.

Regards,

Todd